Design Round 7 · Deliverable 1 · The Project · renders canon 2026-07-11 · July 11, 2026
The Project — the organizing spine
A Project is a first-class primitive within an Organization: it connects tools, agents, and software systems, it interacts with Claude Code and Codex, and it is Studio's central organizing principle. This canvas designs one real Project throughout — The Ceremony Machine's Lightbrush integration: Moe's tools (Dowbot, Digital Dolly, RenderDeck) coming in as connected systems, Elias's integration work passing to Claude Code as packages and returning as recorded artifacts. Creation (1a), anatomy (1b), the ally's narration against the Field's place (1c), and ACTIONS when the Project needs a human (1d).
1a
Creation — a duna command with its receipt, not a wizard
A Project is created in conversation, inside the Organization it belongs to. The ally states the exact command before running it; the receipt is a machine-generated sentence over that command. No gold: creating a Project is a recorded act, not a signed one — the three signed acts at launch stand (join · code extension · domain binding), and R7 proposes only one addition, at 04 · 4e.
Kiduna Studio · Chat
container · The Ceremony Machine
Start a Project here for the Lightbrush integration. Elias runs it; Moe brings the tools in.
Here's the command I'll run in The Ceremony Machine's scope — say go, or change anything:
project.create(org: the-ceremony-machine,
name: "Lightbrush integration",
purpose: "bring Lightbrush's creative stack in as connected systems",
lead: elias, members: [moto, moe])
Go.
receipt · recorded in The Ceremony Machine
The Ceremony Machine now has a Project named Lightbrush integration, led by Elias, with Moto and Moe as members. It holds nothing yet: no tools connected, no grants beyond membership, no Records.
over: project.create(org: the-ceremony-machine, …) · 2026-07-11 09:41 · recorded
It also has a place now — an on-the-fly Scene in the Field, in The Ceremony Machine's grounds. It will look like words and pixels until someone gives it better. That's honest.
the command is stated before it runs · the receipt is a sentence over the exact command · light (mint) announces what happened; gold is reserved for signatures
A Project is born the way everything is born here: someone says it to their ally, inside a container, and the graph records exactly what was said and done.
Why no gold: a Project binds no one and spends nothing at creation. The moment a Project's work needs a person's name on it is later — acceptance of returned work (04 · 4e) — and that's where the ceremony question lives.
Decided and flagged (OQ-1): every Project gets a Scene in the Field at creation, at the on-the-fly grade. The alternative — Projects as objects inside the Organization's one Scene — is argued in 1c and OPEN-QUESTIONS.
1b
Anatomy — the Project card, front and back
The card grammar since R3: front = consequence, back = context. The front answers "what is this Project doing and who can do what"; the back answers "where did all of this come from." Six weeks into the Lightbrush integration, the card looks like this.
project · The Ceremony Machine
active · work out
Lightbrush integration
Bring Lightbrush's creative stack into The Ceremony Machine as connected systems, so the festival's shows can be built with Moe's tools under the duna's own grants.
members · grants
Elias · leadpackage out · record · connect systems
Moe · member (Lightbrush LLC, institution)connect own systems · credentials
Moto · memberread · accept on the duna's behalf
connected systems
Dowbot · registered
Digital Dolly · registered
RenderDeck · unregistered
Claude Code · local, Elias's machine
Records
23
packages
6
one in flight
front — what it does, who may do what, what's connected, what's moving
back · where this came from
Created 2026-07-11 by Moto · project.create(org: the-ceremony-machine, …) · receipt on file
Dowbot, Digital Dolly registered 07-14 by Moe under Lightbrush LLC's institution agreement — IP stays Lightbrush's; usage-based distributions per the duna's recorded configuration
RenderDeck connected 07-18, unregistered — it works inside this Project's grants; registration is Moe's to do, or not (
03 · 3c)
23 Records — every one cites its source: 14 to returned packages, 6 to uploads, 3 to conversation. Nothing in this Project is unattributed.
State is derived, never declared: "active · work out" means a package is currently with Claude Code on Elias's machine — remove the package, the state changes itself
correction is conversational — tell your ally what's wrong; removal is forgetting, not hiding
back — citations, agreements, and the rule that state is derived from the graph
A Project's anatomy is five things: purpose (member-authored, verbatim) · members and their grants (stated, scoped, revocable in a sentence) · connected tools, agents, and systems (each registered or unregistered, said plainly) · Records (all cited) · state (derived).
Institutions show their shape here: Moe participates as a member; Lightbrush LLC's standing is an institution agreement recorded in the duna, not a special UI. The card just says so.
Numbers on the card are in Goudy because they're alive — they change when the graph changes, never because someone typed a new number.
1c
The ally narrates it; the Field shows it as a place
DECIDED · a Scene per Project — flagged, OQ-1
Same Project, both renderings, side by side in Studio (the side-by-side layout from 02 · 2a). In Chat, Taro narrates the Project's life as events with citations. In the Field, the Project is a Scene — a bounded workroom in The Ceremony Machine's grounds where uploads, tools, packages, and people are somewhere.
Kiduna Studio
project · Lightbrush integration
Field · both · Chat
the Field · Scene: Lightbrush integration · drawn live
RenderDeck · unregistered
package · out with Claude Code
The Ceremony Machine · Lightbrush integration
open the package
ask RenderDeck's status
Taro — the package has been out 40 minutes; RenderDeck still needs Moe's credentials.
chat · Taro narrates the Project
This morning: Moe registered Digital Dolly under the Lightbrush agreement · cited to the registration record. Elias sent the adapter work out as a package · cited to package #6.
What's left before the first show can use Dolly?
Two things, one yours: the adapter returns and someone accepts it into the record — and RenderDeck needs credentials only Moe holds. I've surfaced that to him as an ACTION (
1d).
the same graph, told — every narrated event cites the Record it narrates
desktop 1440 (shown scaled) · side-by-side layout · the Scene is on-the-fly grade: dashed ground, "drawn live" chip standing, nothing drawn that a sentence didn't state
Chat and the Field are two renderings of one graph: the ally tells the Project; the Field is the Project, somewhere.
A Scene per Project (decided, OQ-1): a Project is bounded work with its own members, grants, and things — exactly what a Scene is for. It starts at the on-the-fly grade and climbs the ladder only if someone inside cares to raise it (02 · 2c). The room being rough while the work is young is signal, not shame.
Registered vs unregistered renders as line quality, not as warnings: solid borders for registered systems, dashed camel for unregistered ones. Same room, stated difference, no fear language.
1d
ACTIONS — when the Project needs a human
An ACTION is the Project stopping to wait for a person. It appears in the Field and in Chat — same act, two renderings — addressed to the one member who can perform it. Here: RenderDeck can't connect without credentials only Moe holds.
in the Field · Moe's view
action · yours
RenderDeck needs its credentials to work inside this Project. Only you hold them.
provide credentials
in the Field, the ACTION sits at the thing it's about — the sky rim marks it touchable; it never pulses
in Chat · Moe's ally, for Moe
The Lightbrush integration is waiting on one thing that's yours: RenderDeck's credentials. Elias's adapter can't run against it until they're in.
action · RenderDeck credentials
Held at secret in your own space; the Project gets use, never the keys. Revocable in one sentence.
provide credentialsnot now
"not now" is a real answer — the ACTION stands, silent, until performed or withdrawn; it never counts, never nags
in Chat, the same ACTION arrives through the member's own ally — never from someone else's
The ACTION grammar: addressed to one member · states what it needs and why in two sentences · states the access consequence in its own label · offers the act and "not now" · appears where the member is (Field or Chat), never in both loudly.
No queue, no inbox, no badge counts. Standing ACTIONS are visible in the Project card's front and by asking your ally "what's waiting on me" — the docket pattern from Concepts, kept conversational.